fix: use full output-path on convert mdapi
#1091
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fix a bug where
project convert mdapi --output-dir path/to/output
would save the converted metadata topath
instead ofpath/to/output
if the path didn't exist before.When the dir doesn't exist we create it for the user but the code was returning
fs.promises.mkdir
response which only returned the first dir in the path:https://nodejs.org/api/fs.html#fspromisesmkdirpath-options
Updated convert NUT to check that the filepath starts with the full output path.
What issues does this PR fix or reference?
@W-15097291@